|
|
|
|
|
|
|
Figure 12.3.
An example of a facade. |
|
|
|
|
|
|
|
|
The Customer, Account, and CashDepositRecord classes are part of the Business Rules Subsystem. The two forms are part of the Graphical User Interface Subsystem. TransactionProcessor, then, is not only a controller for the two forms but also, effectively, a facade between the Graphical User Interface Subsystem and the Business Rules Subsystem. |
|
|
|
|
|
|
|
|
Incorporating into the Samsona Bank Teller System Example |
|
|
|
|
|
|
|
|
Now that you have completed your controller classes and GUI requirements, you can create the subsystem. You simply need to create the forms in the Visual Basic development environment and generate the code for the controllers in Visual Modeler. The generated code is nothing more than empty classes, methods, and properties. The code listing in the next section shows the code for the Samsona Bank Teller System that includes only the forms and form controllers. |
|
|
|
|
|
|
|
|
As for the forms, use the described fields and buttons in this chapter to create them. The forms listed in the subsequent text will give you an idea of mapping the use cases in the continuing Bank example into the visual presentation that your user sees. The complete list of forms is as follows: |
|
|
|
|
|
|
|
|
frmDeposit (Figure 12.4)
frmOpenAccount (Figure 12.5)
frmWithdraw (Figure 12.6)
frmCloseAccount (Figure 12.7)
frmCancelTransaction (Figure 12.8)
frmCheckAccountStatus (Figure 12.9)
frmMDI (Figure 12.10)
frmAccountDetail (Figure 12.11)
|
|
|
|
|
|
